🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

🧪 CI tested the following changed modules:

• parent

✅ POM dependency changes: targeted tests included

Changed properties: fory-version

⚙️ View full build and test results

upstream issue apache/fory#3788

I think we can go with providing the parameter in the maven surefire test, document that when using camel fory the parameter --add-opens=java.base/java.lang.invoke=ALL-UNNAMED is required and mention it as a breaking change in the upgrade guide

I think we can go with providing the parameter in the maven surefire test, document that when using camel fory the parameter --add-opens=java.base/java.lang.invoke=ALL-UNNAMED is required and mention it as a breaking change in the upgrade guide

okay that is good

@dependabot rebase

created a PR from a branch from my fork #24317 because I'm unable to push on Apache repo today

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

Fory 1.4.0 will add an Unsafe-based fallback path to get privileged invoke access, so I think it is reasonable to hold this upgrade for now and wait for the next Fory release.

Longer term, though, it would still be good to support opening java.base/java.lang.invoke on JDK 25+, since Unsafe is increasingly restricted and may become unavailable in a future JDK. If that happens, java.lang.invoke is likely to be the only practical fallback path for this kind of low-level access.